WIP: [Storage] Refactor test_clone tests to remove DV wait usage#4605
WIP: [Storage] Refactor test_clone tests to remove DV wait usage#4605ema-aka-young wants to merge 1 commit intoRedHatQE:mainfrom
Conversation
…sage and utilize create_dv for DataVolume creation Signed-off-by: Emanuele Prella <eprella@redhat.com>
📝 WalkthroughWalkthroughTest simplification in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Report bugs in Issues Welcome! 🎉This pull request will be automatically processed with the following features: 🔄 Automatic Actions
📋 Available CommandsPR Status Management
Review & Approval
Testing & Validation
Container Operations
Cherry-pick Operations
Label Management
✅ Merge RequirementsThis PR will be automatically approved when the following conditions are met:
📊 Review ProcessApprovers and ReviewersApprovers:
Reviewers:
Available Labels
AI Features
💡 Tips
For more information, please refer to the project documentation or contact the maintainers. |
|
|
||
| with DataVolume( | ||
| name="dv-target", | ||
| with create_dv( |
There was a problem hiding this comment.
There may be an issue with WFFC storage.
create_dv() creates a first consumer pod, which may put a PVC on a certain node, and if this node cannot accommodate our future VM, VM will never be scheduled.
The expected WFFC flow is to create a DV, leave it without the consumer, and then VM that wants to use it becomes its first consumer.
There was a problem hiding this comment.
Got it, thank you. I'll revert this change.
There was a problem hiding this comment.
@jpeimer After some investigation, I noticed we could avoid having the dummy consumer pod setting consume_wffc to False
And we could have a conditional wait for DV success or pending population, depending on the storage class binding. Like we have in
openshift-virtualization-tests/tests/storage/cdi_import/conftest.py
Lines 163 to 166 in 86f63e3
What do you think of this approach?
|
/wip |
Short description:
Removing DataVolume wait usage to allow us to remove it from the wrapper. Using
wait_for_dv_success()instead.More details:
Part of this task's work https://redhat.atlassian.net/browse/CNV-73197
What this PR does / why we need it:
To abandon DataVolume wait(), which will be deprecated.
Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:
Summary by CodeRabbit